We've been struggling a long time with mmseqs modules which wouldn't run with the GTDB database (in the nf-core/funcscan pipeline in our case). The reproducible error occurred always late in the "prefilter" step of the mmseqs runs with infos like aggregatetaxweights died.

@Darcy220606 recently solved the mystery:

[The flag] --compressed 1 is hardcoded across all mmseqs module on nf-core, that apparently is creating a problem when no contigs pass the prefilter step at a certain kmer size, which is a bit downstream in the general prefilter process (esp. that we have a relatively strict parameters). This confuses the tool as the files are 'emptily compressd'.

Hence, we ran all modules with the --compressed 1 removed and now they run through successfully even with the big GTDB database.
Taking this as confirmation, the flag is removed in all mmseqs modules in this PR. The flag can then be re-added as a parameter on pipeline level if needed.

PR checklist

Closes #XXX

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda